home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_0799
/
687
< prev
next >
Wrap
Text File
|
1994-08-27
|
2KB
|
43 lines
Subject: Re: Home Baked
Date: Tue, 05 Jul 1994 11:43:35 +1000
From: Warwick Allison <warwick@cs.uq.oz.au>
Precedence: bulk
Annius Groenink wrote:
>
>Warwick's WM_TOPPED approach is witty but not perfect---the click only
>gets sent to the app when the mouse button is released. And I am sure
>there IS an Atari document which says: TOP your window when a WM_TOPPED
>message is received! Users expect the action of left-clicking to top a
>window---otherwise they'd be using WINX anyway.
I think I gave the precedence cases at the time:
1. PageStreams toolbox - WM_TOPPED used for click-on-tool.
2. Any other toolbox must work that way too. (eg. Kandinsky, Calamus)
3. Any system that uses modal dialogs where WM_TOPPED messages
for any window just cause topping of the modal dialog.
True, it is slightly imperfect, but it lets non-WINX, non-MTOS users get
the same benefits as those users, and frees us programmer to providing
a consistent interface.
For example, implementing a toolbox-in-a-window model without this
feature is extremely frustrating for the user: every time the want to
change tools they must click on the toolbox window (to top it), then
click on the toolbox window again (to select tool), then click on the
document window again (to top it), then finally click on the document
window to actually use the tool!!! With my WM_TOPPED handling approach,
the user just click on the tool, then uses it. Unbeatable(tm).
>(Although I haven't adopted that approach in Edith... I am a WINX user
>myself, so I just set WF_BEVENT to 1 and trouble gone)
And isn't it nice. So don't deprive those poor non-WINX/non-MTOS users
of the feature.
--
Warwick